Great product, easy to use, careful use of autoscaling
We use Azure Web Apps for our Front End and some big data processing needs: for the monolith and some microservices. Also we host APIs …
Starting at $9.49 per month
View PricingOverview
What is Azure App Service?
The Microsoft Azure App Service is a PaaS that enables users to build, deploy, and scale web apps and APIs, a fully managed service with built-in infrastructure maintenance, security patching, and scaling. Includes Azure Web Apps, Azure Mobile Apps, Azure…
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Shared Environment for dev/test
$9.49
Cloud
per month
Basic Dedicated environment for dev/test
$54.75
Cloud
per month
Standard Run production workloads
$73
Cloud
per month
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://azure.microsoft.com/en…
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $9.49 per month
Product Details
- About
- Tech Details
- FAQs
What is Azure App Service?
Azure App Service Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
The Microsoft Azure App Service is a PaaS that enables users to build, deploy, and scale web apps and APIs, a fully managed service with built-in infrastructure maintenance, security patching, and scaling. Includes Azure Web Apps, Azure Mobile Apps, Azure API Apps, allowing developers to use popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP, and Ruby.
Azure App Service starts at $9.49.
Reviewers rate Development environment replication highest, with a score of 10.
The most common users of Azure App Service are from Small Businesses (1-50 employees).
Comparisons
Compare with
Reviews and Ratings
(169)Attribute Ratings
Reviews
(1-4 of 4)Companies can't remove reviews or game the system. Here's why
March 30, 2024
Great product, easy to use, careful use of autoscaling
We use Azure Web Apps for our Front End and some big data processing needs: for the monolith and some microservices. Also we host APIs over them. Web Apps offer an easy to use platform for creating and modifying our code in a seamless way across different stages of our data ingestion-processing-and offering for the customers.
- Extremely easy to deploy and update from Visual Studio
- It integrates seamlessly with other Azure PaaS resources
- It has an in-depth integration with AppInsights, so you can understand errors and their root cause easily.
- Easy to create and delete, what is not the same case in a IaaS resource
- It escalates based on CPU workload and some other resource variables.
- Configuration changes are almost immediate
- Offers an excellent abstraction from hardware backend of the platform
- That's updated very often, saving time and the risk of a self-performed update over a IaaS
- That's really easy to develop for Web Apps
- It supports Function Apps and Web Apps into the same "cost black box"
- Irrationally expensive
- High latency and poor response times in heavy workloads
- Some updates lead to failures and crashes of hosted apps
- Tech support starts defending Microsoft rather than helping you to get rid of a production failure
- That's easy to have a peak cost with automatic resources escalation.
- Lacks of spent money limits for escalation
- Unnecessary deprecation of runtimes that makes the platform less interesting for complex applications that can't be updated periodically
- Every single minor feature that's an spending. For example, a basic firewall.
80%
8.0
- When workload was medium-low and medium-high it escalated and performed in a very good way. We saved a lot of time and a specialized role for managing it. Also, compared to an IaaS solution, was reasonably expensive.
- Many platform issues on 2020 caused problems with our business. Downtime was reimbursed, but some customers were lost and churn grew.
- Using AppServices and Web Apps as a Big Data processing platform was not a good idea, specially when data volumes grew and every escalation in resources was 2x of the previous stage cost.
AppServices that's easier to manage than its competitors, specially if you have everything in Azure. But also that's the most expensive service when you escalate or start using it for massive data processing. It would be an excellent containers platform if were easier to deal with its costs.
Regarding Apache and AKS, also I must mention the required level of manual maintenance that's a key point. If you wont have internally or via consulting a specialized role, AppServices that's the best choice.
Regarding Apache and AKS, also I must mention the required level of manual maintenance that's a key point. If you wont have internally or via consulting a specialized role, AppServices that's the best choice.
The ASP NET Core apps were deployed using Azure App Service. Multiple programs were installed and utilized by the entire company. Having the ability to launch our apps directly from Visual Studio was a huge time-saver. The Azure site or the Azure command-line interface allowed us to make the necessary adjustments.
- Visual Studio makes it an easy to deploy an app.
- The Azure CLI and the Azure Portal are the two most convenient ways to interact with the cloud.
- There's no need to worry about server upkeep. We could simply increase our capacity by changing a few gateway settings.
- Like Heroku's dynos, abstraction of computing resources.
- The total size of the Azure Portal has a negative impact on the management of Azure App Service apps.
- The cost of making large transitions in the size of a resource is high.
- Auto scaling.
- Azure Kubernetes.
- CI/CD pipelines for DevOps development.
87.27272727272727%
8.7
- Deployment of ASP.NET apps at the organization has been sped up.
- An option to offer access to the version control system on a third platform so that we could easily deploy our apps.
- Because of Azure App Service's scalability capabilities, the costs of running the services are kept to a minimum. As a result, we may save hundreds of dollars each month compared to the expenses of traditional servers by using fewer resources during slack periods.
In terms of deploying your apps, Azure App Service provides a solid foundation. You may use either the Azure command-line interface or the Web Portal to administer these apps. As a whole, I find You may easily deploy your apps to Azure App Service to be a really difficult platform for novices to get their feet wet. First and foremost, I'd look at Heroku's user interface and the way it abstracts compute units.
We use Azure App Service to build full-fledged custom web-based software solutions for small and medium-sized businesses in a variety of markets. The Azure App Service coupled with .NET, Entity Framework, and other Azure features (storage, tables, etc.) make it easy to quickly build fully-functional apps, and we're able to do so so much quicker than when we were using the LAMP stack (Linux, Apache, MySQL, and PHP). Plus, we can scale resources with a click instead of needing to migrate to different servers and manually handle load balance, etc.
- Super quick & easy to deploy new apps in visual studio
- Easy scaling to help reduce costs during off-hours
- The powerful Azure ecosystem offers a lot of functionality that ties in well with Azure App Service
- Jumps between resource sizes can get expensive
- You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
- Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).
- Azure App Service has allowed us to quickly deploy high-budget projects very quickly, netting us a healthy profit vs the cost to develop. (We make, on average, about 10x what it costs to get up and running per project thanks to how easy it is to implement a skeleton framework.)
- Costs are low to run the services thanks to the scaling functionality that comes with Azure App Service. We can utilize less resources during slow times and save hundreds of dollars per month vs costs of traditional servers.
November 27, 2019
Azure App Service, a great platform - yet a bit complex interface
During my time at the company, Azure App Service was used to deploy ASP NET Core applications. It was used throughout the whole organization and we had multiple applications deployed there. It was pretty useful since we could deploy our applications directly from Visual studio, never leaving our code editor environment. We could modify the settings from the Azure portal or with the Azure command-line interface.
- Simple app deployment from Visual Studio.
- Easy interfaces: Azure CLI and Azure Portal.
- No server maintenance. We could scale easily by just modifying some settings in the portal.
- Abstraction of computing resources like Heroku does with dynos.
- Azure Portal overall is pretty bloated and that affects managing Azure App Service applications.
- Reduced the deployment time of ASP .NET applications in the company.
- Gave us an alternative to quickly deploy our applications without granting access to the version control system to a third platform.
Azure App Service will give you a very solid and strong platform to deploy your applications. It gives you great interfaces to manage those applications either through a Web Portal or the Azure command-line interface. However, I consider Azure overall to be very complex and hard for newcomers to use it right away. I would consider Heroku first due to its extremely simple interface and abstraction of computing units.